Bump onnxruntime to 1.24.4 and add Python 3.14 by jviehhauser · Pull Request #177 · conda-forge/onnxruntime-feedstock

jviehhauser · 2026-04-01T20:18:00Z

Summary

Bumps onnxruntime from 1.24.2 to 1.24.4
Adds Python 3.14 support (drops Python 3.10 — upstream now requires >= 3.11)
Switches Linux runners from decommissioned cirun-openstack-cpu-4xlarge to Cirrus runners (ghcr.io/cirruslabs/ubuntu-runner-amd64:24.04-lg)
Removes deprecated self_hosted from conda-forge.yml (fixes linter warning)
Re-rendered with conda-smithy 3.59.0

Motivation

The Python 3.14 migration PR (#163) was blocked by a segfault in onnxruntime on Python 3.14 (upstream issue microsoft/onnxruntime#27392). This was fixed upstream in v1.24.3 via microsoft/onnxruntime#27413 (refcount bug in map input conversion). The reporter confirmed the fix on win-64, linux-64, and osx-arm64.

v1.24.4 is a patch release containing additional bug fixes. It also bumps python_requires to >= 3.11, so Python 3.10 is dropped from the build matrix.

All 4 existing patches were verified to still apply cleanly to v1.24.4.

CI runner changes

The Quansight Open GPU Server (OpenStack) was decommissioned on 2026-03-13 (conda-forge/.cirun#174), causing all Linux GHA jobs to time out after 24h waiting for runners that no longer exist. This PR switches Linux builds to Cirrus runners (access granted via conda-forge/admin-requests#1982). Windows builds remain on cirun-azure-windows-4xlarge.

Supersedes #163 and #176.

Test plan

osx-arm64 builds pass (all Python versions including 3.14)
Linux builds pass on Cirrus runners
Windows builds pass on cirun-azure
Python 3.10 builds are correctly skipped

conda-forge-admin · 2026-04-01T20:19:35Z

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found some lint.

Here's what I've got...

For recipe/meta.yaml:

❌ In conda-forge.yml: $.github_actions = {'self_hosted': True, 'timeout_minutes': 720, 'triggers': ['push', 'pull_request']}.

{'self_hosted': True, 'timeout_minutes': 720, 'triggers': ['push', 'pull_request']} is not valid under any of the given schemas
Schema
```
{
  "anyOf": [
    {
      "$ref": "#/$defs/GithubActionsConfig"
    },
    {
      "type": "null"
    }
  ]
}
```

For recipe/meta.yaml:

ℹ️ The recipe is not parsable by parser conda-souschef (grayskull). This parser is not currently used by conda-forge, but may be in the future. We are collecting information to see which recipes are compatible with grayskull.
ℹ️ The recipe is not parsable by parser conda-recipe-manager. The recipe can only be automatically migrated to the new v1 format if it is parseable by conda-recipe-manager.

_{This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/23869425105. Examine the logs at this URL for more detail.}

Version bump from bot PR conda-forge#176.

- Add python314 migration yaml - Add skip for py < 311 (upstream requires python >= 3.11 since 1.24.4) - Re-rendered with conda-smithy 3.58.1

jviehhauser · 2026-04-01T20:48:14Z

@conda-forge-admin, please rerender

conda-forge-admin · 2026-04-01T20:52:06Z

Hi! This is the friendly automated conda-forge-webservice.

I tried to rerender for you, but it looks like there was nothing to do.

_{This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/23870122707. Examine the logs at this URL for more detail.}

conda-forge-admin · 2026-04-01T20:52:24Z

Hi! This is the friendly automated conda-forge-webservice.

I tried to rerender for you, but it looks like there was nothing to do.

_{This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/23870136963. Examine the logs at this URL for more detail.}

Self-hosted runners are already configured via github_actions_labels in conda_build_config.yaml. The deprecated self_hosted key was triggering linter warnings.

conda-forge-admin · 2026-04-01T21:07:08Z

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found it was in an excellent condition.

I do have some suggestions for making it better though...

For recipe/meta.yaml:

ℹ️ The recipe is not parsable by parser conda-souschef (grayskull). This parser is not currently used by conda-forge, but may be in the future. We are collecting information to see which recipes are compatible with grayskull.
ℹ️ The recipe is not parsable by parser conda-recipe-manager. The recipe can only be automatically migrated to the new v1 format if it is parseable by conda-recipe-manager.

_{This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/24240523236. Examine the logs at this URL for more detail.}

cbourjau · 2026-04-02T21:55:44Z

Do we expect the GitHub-hosted runners to be beefy enough to build the CUDA builds? Either way, the cirun ones are still referenced here. I don't think that this is ready, is it?

conda-forge-admin · 2026-04-02T23:24:33Z

Hi! This is the friendly conda-forge automerge bot!

I considered the following status checks when analyzing this PR:

linter: passed
azure: passed
github-actions: failed

Thus the PR was not passing and not merged.

cbourjau · 2026-04-07T09:13:59Z

conda-forge/admin-requests#1982 provides an alternative for the Linux runners, but I'm not sure what the solution for Windows is, yet. Either way, this PR is not ready to be merged.

The Quansight Open GPU Server (OpenStack) was decommissioned on 2026-03-13 (conda-forge/.cirun#174), so cirun-openstack-cpu-4xlarge runners no longer exist. All Linux GHA jobs were timing out after 24h waiting for runners that will never come. Cirrus runners access was granted via conda-forge/admin-requests#1982. This switches Linux builds to ghcr.io/cirruslabs/ubuntu-runner-amd64:24.04-lg (16 CPUs, 48GB RAM). Windows builds remain on cirun-azure-windows-4xlarge. Re-rendered with conda-smithy 3.59.0.

jviehhauser · 2026-04-07T11:24:31Z

Updated to switch Linux builds to Cirrus runners (see also conda-forge/.cirun#174). Windows builds remain on cirun-azure-windows-4xlarge for now.

…ers" This reverts commit 13600fe.

…rus runners"" This reverts commit 4e17431.

0xbe7a · 2026-04-09T13:20:06Z

Is this PR for now just blocked on maintainer approval for the workflow run, or are there other blockers? If it’s just that, can @janjagusch or @cbourjau approve it please?

diegoferigo-rai · 2026-04-09T15:45:43Z

@jviehhauser would it be possible to activate linux-aarch64 GPU entries in the build matrix? As I did in:

Try compiling cuda version on linux-aarch64 #172.

Relevant comment: #172 (comment).

Remove the skip directive that blocked CUDA builds on aarch64, as cross-compilation has been verified to work (see PR conda-forge#172).

jviehhauser · 2026-04-10T09:49:49Z

@diegoferigo-rai Done — removed the skip directive for linux-aarch64 CUDA builds (as per your commit in #172).

@conda-forge-admin, please rerender

…6.04.09.16.37.5

cbourjau · 2026-04-10T10:23:11Z

@jviehhauser please reduce the build matrix to something minmal first (e.g. only python 3.14 and no -novec) so that we can try out the aarch64 builds.

cbourjau · 2026-04-10T10:25:58Z

Is this PR for now just blocked on maintainer approval for the workflow run, or are there other blockers? If it’s just that, can @janjagusch or @cbourjau approve it please?

We don't have a way to build for Windows+CUDA, currently. We can't merge this as is. We either have to drop those builds or wait a little longer to see how this is resolved upstream (my preference).

Minimize the build matrix to test aarch64 CUDA builds before expanding back to the full matrix.

jviehhauser · 2026-04-10T11:19:38Z

@conda-forge-admin, please rerender

…6.04.09.16.37.5

diegoferigo-rai · 2026-04-10T11:32:35Z

We don't have a way to build for Windows+CUDA, currently. We can't merge this as is. We either have to drop those builds or wait a little longer to see how this is resolved upstream (my preference).

Would it make sense to drop the currently unavailable platforms for now and reintroduce them later? If resolving this upstream takes several weeks, blocking all other builds seems unnecessary. Updated CUDA linux-aarch64 binaries have already been missing for a while, it would be great to move forward in the meantime.

jviehhauser added 2 commits April 1, 2026 22:29

Bump onnxruntime to 1.24.4

1c8e7ce

Version bump from bot PR conda-forge#176.

Add Python 3.14 support, drop Python 3.10

ad3d170

- Add python314 migration yaml - Add skip for py < 311 (upstream requires python >= 3.11 since 1.24.4) - Re-rendered with conda-smithy 3.58.1

jviehhauser force-pushed the bump-1.24.4-py314 branch from 2d4d184 to ad3d170 Compare April 1, 2026 20:31

Remove deprecated self_hosted from conda-forge.yml

4e707e6

Self-hosted runners are already configured via github_actions_labels in conda_build_config.yaml. The deprecated self_hosted key was triggering linter warnings.

jviehhauser marked this pull request as ready for review April 1, 2026 21:08

jviehhauser requested review from cbourjau, hmaarrfk, janjagusch, jtilly, traversaro and xhochy as code owners April 1, 2026 21:08

hmaarrfk added the automerge Merge the PR when CI passes label Apr 1, 2026

cbourjau removed the automerge Merge the PR when CI passes label Apr 7, 2026

jviehhauser added 2 commits April 7, 2026 13:48

Revert "Switch Linux runners from dead cirun-openstack to Cirrus runn…

4e17431

…ers" This reverts commit 13600fe.

Revert "Revert "Switch Linux runners from dead cirun-openstack to Cir…

d7b4672

…rus runners"" This reverts commit 4e17431.

Enable linux-aarch64 CUDA builds

55d8c83

Remove the skip directive that blocked CUDA builds on aarch64, as cross-compilation has been verified to work (see PR conda-forge#172).

MNT: Re-rendered with conda-smithy 3.59.1 and conda-forge-pinning 202…

48d7e9f

…6.04.09.16.37.5

Temporarily reduce build matrix to Python 3.14 only, no -novec

ec15846

Minimize the build matrix to test aarch64 CUDA builds before expanding back to the full matrix.

MNT: Re-rendered with conda-smithy 3.59.1 and conda-forge-pinning 202…

36deaac

…6.04.09.16.37.5

Uh oh!

Conversation

jviehhauser commented Apr 1, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Motivation

CI runner changes

Test plan

Uh oh!

conda-forge-admin commented Apr 1, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

jviehhauser commented Apr 1, 2026

Uh oh!

conda-forge-admin commented Apr 1, 2026

Uh oh!

conda-forge-admin commented Apr 1, 2026

Uh oh!

conda-forge-admin commented Apr 1, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

cbourjau commented Apr 2, 2026

Uh oh!

conda-forge-admin commented Apr 2, 2026

Uh oh!

cbourjau commented Apr 7, 2026

Uh oh!

jviehhauser commented Apr 7, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

0xbe7a commented Apr 9, 2026

Uh oh!

diegoferigo-rai commented Apr 9, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

jviehhauser commented Apr 10, 2026

Uh oh!

cbourjau commented Apr 10, 2026

Uh oh!

cbourjau commented Apr 10, 2026

Uh oh!

jviehhauser commented Apr 10, 2026

Uh oh!

diegoferigo-rai commented Apr 10, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

6 participants

jviehhauser commented Apr 1, 2026 •

edited

Loading

conda-forge-admin commented Apr 1, 2026 •

edited

Loading

conda-forge-admin commented Apr 1, 2026 •

edited

Loading

jviehhauser commented Apr 7, 2026 •

edited

Loading

diegoferigo-rai commented Apr 9, 2026 •

edited

Loading